chore: release 1.16.1 - #237
Closed
fedemaleh wants to merge 1 commit into
Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Cuts
1.16.1, a single-fix patch over1.16.0(tagged earlier today): #236 stopsk8s/instance/listfrom always capping at the first 10 pods, so the performance view of a scope with more than 10 pods shows all of them.Do not merge or tag before #236. That PR is still a draft with review pending; tagging
v1.16.1without it would ship a CHANGELOG entry describing a fix the tree does not contain.CHANGELOG only, per this repo's release convention — nothing else in the tree references the version (
grep 1.16.0finds only the CHANGELOG header). Existing entries were not reordered, reworded or touched, and no emptyUnreleasedsection is introduced.Note for whoever tags: the tag carries the
vprefix (v1.16.1); the CHANGELOG and the customer-facing release message do not.